fix: routes controller on node name drift#1221
Merged
Merged
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1221 +/- ##
==========================================
+ Coverage 69.95% 70.62% +0.67%
==========================================
Files 24 24
Lines 2656 2676 +20
==========================================
+ Hits 1858 1890 +32
+ Misses 629 609 -20
- Partials 169 177 +8
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
lukasmetzner
force-pushed
the
fix/routes-controller-node-name-drift
branch
from
0e99446 to
19d6cf7
Compare
lukasmetzner
force-pushed
the
fix/routes-controller-node-name-drift
branch
from
19d6cf7 to
1382b4c
Compare
lukasmetzner
had a problem deploying
to
e2e-robot
GitHub Actions
Failure
lukasmetzner
force-pushed
the
fix/routes-controller-node-name-drift
branch
from
08a2e3f to
ea742f6
Compare
lukasmetzner
force-pushed
the
fix/routes-controller-node-name-drift
branch
from
ea742f6 to
eb55116
Compare
apricote
reviewed
May 18, 2026
If a Kubernetes node got successfully initialized we have the Server ID stored in the node objets `providerID`. When renaming a Server, causing a drift between the node and Server name, we should still be able to identify the Server via its ID. This is currently not implemented in the routes' controller, where we rely purly on the Servers name. As the upstream library only provides us with the Kubernetes node name and not the full object, we have to first fetch it from the Kubernetes API. With the node object at hand we can identify and fetch the Server by its ID. Furthermore, we can use the Kubernetes node object to improve our handling of Kubernetes events. The event emitted on a CIDR mismatch is currently not associated with the affected node, because so far we did not have access to the nodes UUID.
lukasmetzner
force-pushed
the
fix/routes-controller-node-name-drift
branch
from
eb55116 to
0796918
Compare
apricote
approved these changes
May 19, 2026
|
hot damn! Quite the short turnaround time on such a big change! I'm impressed and very grateful. Thank you 🙏 |
Contributor
Author
|
Took the opportunity to clean up some old code :D |
lukasmetzner
pushed a commit
that referenced
this pull request
May 19, 2026
### Bug Fixes - routes controller on node name drift (#1221)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
If a Kubernetes node got successfully initialized we have the Server ID stored in the node objets
providerID. When renaming a Server, causing a drift between the node and Server name, we should still be able to identify the Server via its ID. This is currently not implemented in the routes' controller, where we rely purly on the Servers name.As the upstream library only provides us with the Kubernetes node name and not the full object, we have to first fetch it from the Kubernetes API. With the node object at hand we can identify and fetch the Server by its ID. Furthermore, we can use the Kubernetes node object to improve our handling of Kubernetes events. The event emitted on a CIDR mismatch is currently not associated with the affected node, because so far we did not have access to the nodes UUID.
Fixes #1214